External Packages

There are several packages available on the frontend and in js-slang, making it unnecessary for Source modules to include them when bundled. This PR will further externalize several of these packages (the full list here), reducing the size of files.

In the future, if there are packages that Source modules that require that are also already available at runtime, these packages should also be marked as external, but such changes would also require corresponding updates to the frontenda and/or js-slang

Refinement of Module Scripts

The script system has become increasingly complex. To aid with this I've condensed all the script management code into a single Javascript file. Instead of committing the entire output of compiling module scripts, module scripts can instead be built using the yarn scripts:build command (which should be run automatically on postinstall). Module script functionality remains identical.

yarn test and yarn scripts:test should now both work with Windows paths, where previously Jest only recognized posix style paths as valid patterns.

Error Handling for AnimationCanvas

Animations are calculated at runtime, so there is no way for bundle code to detect beforehand if an animation is invalid or will throw an error. As such, an error screen has been added to the various animation canvases which will allow these to throw errors gracefully. Fixes #225.

Change in throwIfNotRune

Similar to how the functions in sound have been modified to allow for custom function names, the throwIfNotRune function in the rune bundle has also been modified to allow custom function names to be shown when errors are thrown.

Updated typedoc

Typedoc has since fixed the issue where the README was not getting generated with the rest of the HTML documentation. The original README file has thus been re-included.

Documentation Relocation

The summaries that used to be present in the functions.ts files of bundles have been relocated to their entry points. These summaries should now be visible within the HTML documentation. Resolves #221.

Tab Development Server

Currently, the frontend is the only way to render module tabs. This means that every change requires a rebuild of the tab, followed by a refresh on the frontend.

This PR will introduce a Vite server that is able to react to changes in tabs and render them live.

For the server to be able to work, components need to be defined as a separate constant, instead of just within the body() function:

export default {
  body; () => <div></div>
}

should be defined like this:

const Component = () => <div></div>
export default {
  body; () => <Component />
}

Use yarn devserver to start the development server.

Standardize Line Encoding

This PR also incorporates the changes from #210. With the addition of .editorconfig and .gitattributes hopefully development across OSes should be more consistent.